Conversation
|
The mobile version of example app from this branch is ready! You can see it here. |
|
I think we should remove |
|
Thanks for the suggestion @adrcotfas. Addressed the |
|
Hey @xdimota7x, thank you for your pull request 🤗. The documentation from this branch can be viewed here. |
| subtitle, | ||
| subtitleStyle, |
There was a problem hiding this comment.
Since we have removed the usage of subtitle and subtitleStyle we can remove it from the type.
| getLabelText = ({ route }: { route: Route }) => route.title, | ||
| getBadge = ({ route }: { route: Route }) => route.badge, | ||
| getColor = ({ route }: { route: Route }) => route.color, | ||
| getColor: _getColor = ({ route }: { route: Route }) => route.color, |
There was a problem hiding this comment.
Since we are removing the usage of getColor please remove it from the Props or add a dev warning on first call so consumers migrating from 5.x know to drop it.
|
Thank you so much for you work @xdimota7x! |
4 participants
Motivation
This PR removes Material Design 2 support and makes the library MD3-only.
The goal is to simplify the codebase by removing MD2/MD3 branching across components, theming, and utilities, reducing maintenance overhead and inconsistency risk.
Related issue
Paper currently supports both MD2 and MD3, with many conditional code paths (isV3, version-specific theme logic) spread across components and core theming.
This PR addresses that by removing MD2 themes and all associated MD2 behavior/exports.
Test plan